Search through our documentation and learn Spiffy
Billing Automation is one of the most important aspects of running any online business that sells subscriptions or payment plans. These settings make it possible to build an automated follow-up...
The Payment Failed event triggers anytime a subscription payment, or payment plan payment fails. This is the most common event to fire. A charge can fail for a variety of...
The Card Expiring event will trigger two (2) months, or 60 days, before the month their credit card expires. This event is most commonly used to trigger a courtesy reminder campaign that...
The Card Expired event triggers when your customer has not updated their card on file by the end of the month that matches the expiration date on their card. For example, it’s...
The Card Updated event triggers any time your customer has updated their card. If the customer is updating their card after a failed payment has occurred, all unpaid balances will be processed immediately....
In some situations, Stripe will automatically update card info without the customer having to manually update their info. This Card Auto-Updated event makes it possible to run integration actions when...
Hot Swap Setup via Zapier Our Zapier integration allows you to tailor the communication in your follow-ups to include price, product name, the last 4 digits of their CC number,...
We’ve created a streamlined “update card on file” feature, for subscriptions and payment plans. This allows your customers to update their card on file, without having to login to a...
Run automated integration actions based on a Payment Disputed event. When a customer disputes a charge (also known as a chargeback), you can run an action in any of your...
The Payment Plan Completed event actions trigger after your customer’s payment plan has been paid in full. This is most commonly used for internal reporting and notifications, however, you could also send...
The Payment Plan Defaulted event triggers when a customer’s payment has failed and you choose to mark the payment plan as Defaulted. Defaulted status closes out the payment plan and any outstanding...
The Payment Plan Payment event triggers actions after a successful payment plan payment is processed. This is most commonly used for internal processes, to stop customer follow-up, and to send notifications. This...
The Upcoming Payment Plan Payment event triggers actions 7 days prior to your customer billing on an active Payment Plan. This is most commonly used for internal processes, or to trigger an email to...
The “Payment Plan failed payment” event triggers anytime any payment plan payment fails. This event will not trigger by failed subscription payments. This event trigger will run in conjunction with what...
The Payment Plan Resumed event triggers when a payment plan that is in “Unpaid” status is successfully resumed and returns to “Active” status. This can occur internally when you resume...
The Payment Plan Unpaid event triggers after your customer’s payment fails and ALL the auto-charge attempts have also failed. At this point, the payment plan will be moved to an Unpaid/Cancelled status, triggering the Payment Plan...
This event is triggered when a customer’s payment fails due to needing 3D Secure (3DS) verification. How to use this event? This event can be used to trigger any type...
The Product Purchased event is only available for automation on the Product level and will trigger when a Product is purchased. Product level automation is available for Subscriptions and Single...
In your account-level Automation settings, click Add Action, and you will see an event for Purchase. Since this is an account-level setting, all integration actions set up for this Purchase...
Our Refunded Payment events make it possible to automatically trigger actions in your CRM, LMS, or other connected apps when you process a refund in Spiffy. There are two different...
